Conversation
|
@openshift/team-documentation pls review |
|
Hi @sluetze. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
/remove-lifecycle stale |
|
/assign @xiaojiey |
|
This PR applies to OpenShift Docs Versions 4.14+ |
|
@xiaojiey PTAL |
|
/assign @GroceryBoyJr |
|
/label qe-approved |
|
Information needed for COMMENT 0 ABOVE: Version(s): 4.14+ Issue: https://issues.redhat.com/browse/CMP-3759 Link to docs preview: QE review: x QE has approved this change. Additional information: This table update is essential for customers in Germany and in the EU that follow the BSI security standards. Steffen Luetzenkirchen has pushed this information forward and I am facilitating his PR by making sure it satisfies the requirements for publishing. |
|
/retest |
|
/assign @Anna-Koudelkova |
|
/ok-to-test |
|
/retest |
|
🤖 Fri Oct 03 16:53:18 - Prow CI generated the docs preview: |
|
@sluetze: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/label merge-review-needed |
|
/cherrypick enterprise-4.14 |
|
/cherrypick enterprise-4.15 |
|
/cherrypick enterprise-4.16 |
|
/cherrypick enterprise-4.17 |
|
/cherrypick enterprise-4.18 |
|
/cherrypick enterprise-4.19 |
|
/cherrypick enterprise-4.20 |
|
@mburke5678: new pull request created: #100015 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@mburke5678: new pull request created: #100016 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@mburke5678: new pull request created: #100017 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@mburke5678: new pull request created: #100018 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@mburke5678: new pull request created: #100019 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@mburke5678: new pull request created: #100020 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@mburke5678: new pull request created: #100021 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Version(s):
Issue:
Link to docs preview:
QE review:
Additional information:
We had some discussions around this here: https://redhat-internal.slack.com/archives/C04SY4F2RK6/p1748945123014519